Container Orchestration

Each service of the real-time architecture forms a self-contained deployment unit. To do this, each service is encapsulated in its own container with its dependencies, such as the required libraries. The advantage of this is the simplified deployment, because all dependencies of the software encapsulated in the containers are delivered with a software container. This makes it possible to always deploy a service in the same way in production on any system and no dependencies, for example on software versions, have to be taken into account.

Using a separate container for each service also prevents conflicts from arising between the dependencies of individual services. For example, two services could require two different versions of a library. Furthermore, the individual services can be developed, tested and deployed independently of each other. However, one restriction of the system-independent deployment of containers on automation technology devices is the different processor architectures such as ARM or PowerPC, which may have to be taken into account.